-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a schema for self-reporting #1
Conversation
67a0a2e
to
b11f8a9
Compare
Latest iteration in 1a198e9. |
c0ba607
to
1a198e9
Compare
Point from @vladh on a call to use https://en.wikipedia.org/wiki/Well-known_URI |
Add disclaimer to member page
@chadwhitacre I might make some progress on this over the weekend if you're not opposed? |
What are you thinking of working on? The next steps I have in mind are to add real numbers for Sentry and publish the json file on open.sentry.io. The next step after that would be to write the GitHub automations to modify files under |
Sounds good, will do that! |
Light-weight self-reporting is a central part of the OSS Pledge. What should the format be?
Let's define it using JSON Schema for easy validation and interoperability.Going with Zod as part of Astro since that's what we've set up in this repo.(X reachout)
System Design
osspledge.json
on their own domain (thinkrobots.txt
).members.csv
in this repo containingslug,url
for members.members.csv
src/members/{slug}.json
whenmembers.csv
changes.{slug}.json
periodically based on modtime stored therein.